Don't change directory to tmp dir #79
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This looks good to go to me! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When deploying an application to Kubernetes, it's a good practice to configure the filesystem as read only, for security reasons (the filesystem can still be modified outside the container, for instance Vault can automatically rotate credentials which are mounted in the application container).
However,
file_systemuses the functionSystem.tmp_dir!()which fails when the file system is read only:Thus, this PR simply removes the call to
System.tmp_dir!().I'm not 100% that removing this call won't be a problem, but on the other hand, I don't see why a temporary writable directory is useful to interact with
inotifywaitviaPort. Furthermore, my tests shown no problems when removing the directory change.